Add tests for failing private key formats #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rgmz
force-pushed
the
tests/privatekey
branch
9 times, most recently
from
24f2e4f to
e61bab1
Compare
This comment was marked as resolved.
This comment was marked as resolved.
rgmz
force-pushed
the
tests/privatekey
branch
9 times, most recently
from
c0947d9 to
625d9e9
Compare
rgmz
force-pushed
the
tests/privatekey
branch
from
625d9e9 to
c1da84f
Compare
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
TruffleHog doesn't detect a number of private keys. Ideally, it could be more robust in its detection.
Related: gitleaks/gitleaks#1594
Checklist:
make test-community)?make lintthis requires golangci-lint)?